home *** CD-ROM | disk | FTP | other *** search
-
-
-
- - 1 -
-
-
-
- 5. _K_n_o_w_n__P_r_o_b_l_e_m_s__a_n_d__W_o_r_k_a_r_o_u_n_d_s
-
- For the latest information on WebSpace problems and their
- workarounds, please visit
- http://webspace.sgi.com/WebSpace/KnownProblems/1.1/index.html
-
- These are known problems in WebSpace Navigator 1.1.
-
- +o WebSpace can dump core with certain memory limits.
-
- +o Webspace cannot follow relative links if started from
- Mosaic, because Mosaic does not pass the base URL to
- WebSpace. Instead, use Netscape or type URL directly
- into Webspace Open Location dialog.
-
- +o On sites using mime-multipart feature of Netscape,
- Back, Forward and Reload sometimes do not work.
-
- +o WebSpace does not handle Netscape's dynamic documents
- correctly in all situations. The Back, Forward, and
- Reload buttons sometimes do not work.
-
- +o URLs with non-alphanumeric characters sometimes cannot
- be added as a Bookmark from WebSpace. Add these URL's
- directly in Netscape.
-
- +o Multiple webspace viewers can be started when using the
- "server push" feature of Netscape. Exit the extra
- viewers.
-
- +o Webspace may need to be restarted after changing SOCKS
- server in the preferences dialog.
-
- +o Objects sometime clip when moving close to them.
- Seeking to the object or choosing a new view from the
- Viewpoints menu often fixes the problem.
-
- +o When using the trackball (Examiner Viewer) dragging far
- away from ball can cause jittery movement of object.
- It is best to stay within a 1 diameter distance from
- the trackball when moving.
-
- +o Locate highlighting can be visually wrong after the
- window is moved. Change the camera view slightly to
- correct this visual artifact.
-
- +o The walk viewer does not navigate correctly with an
- orthographic camera.
-
- +o When at a viewpoint, clicking the yellow lamp on the
- viewpoint dashboard fixture disables the lamp for an
-
-
-
-
-
-
-
-
-
-
-
- - 2 -
-
-
-
- instant.
-
- +o When going back or forward to a scene, the yellow lamp
- on the viewpoint dashboard fixture will be on, even if
- it shouldn't be.
-
- +o When the WebSpace window width is small, text which is
- displayed in the locate highlight description area can
- be illegible.
-
- +o On Reality Engine with patch154 and Indigo2 with Impact
- graphics textures occasionally are not visible. Reload
- or switching viewers usually solves the problem.
-
- +o The vrmllint utility can hang after finding some
- errors. Cancel vrmllint (control-C) and fix the errors
- in the VRML file, then retry.
-
- +o For some scenes, when using the Options menu to switch
- from Smoothest Motion to either Best Image Quality or
- Smooth Motion, you may get better performance if you
- reload the scene (i.e. hit the Reload button) after
- making the switch.
-
- +o If you bring up the Save dialog, either from the Save
- As... item on the File menu or by hitting the Save
- button on the View Source dialog, select Inventor as
- the format for the saved scene and then hit OK without
- first typing a file name, WebSpace may exit
- unexpectedly.
-
- +o On systems with XZ and Extreme graphics, textures may
- sometimes appear ripped. This problem is most
- noticeable in scenes with two polygons that overlap
- where one polygon is textured and the other is not. A
- workaround is to add the following node at the top of
- the VRML file:
-
- Texture2 {
- image 1 1 1 0xff
- }
-
- This assigns a simple texture to every untextured
- object. This texture does not have any visual effect,
- but it will fix the problem since both polygons are now
- textured. In many cases, this fix will reduce
- rendering performance.
-
- +o On Impact and RealityEngine, textured scenes may not
- draw their textures when you change viewers. This will
- happen if you switch from Walk to Examiner viewer or
-
-
-
-
-
-
-
-
-
-
-
- - 3 -
-
-
-
- vice versa. The textures are not lost, they are simply
- not drawn. This is the subject of an OpenGL bug
- TextureObject which will be fixed in a future OpenGL
- implementation. For now, if you run into this problem,
- you can disable the use of TextureObjects by setting
- the environment variable IV_NO_TEXTURE_OBJECT to 1, and
- restarting the application. This will cause the
- textures to be drawn correctly, but you may see a drop
- in rendering performance.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-